Clone environment

[dabeeeenster]

When creating a new environment, you currently take the default flag states for that project, which are currently not shown anywhere.

It would be better to be able to select which existing environment state you want to clone for the new environment.

[matthewelwell]

As discussed with @gagantrivedi:

We need an endpoint that 'clones' an environment. This should take the existing environment id and a new name for the cloned environment as an input and return the new environment details. Something like:

POST /api/v1/environments/:id/clone

+ request

{
  "name": "<new environment name>"
}

+ Response

{
  "id": <new environment id>,
  "name": "<new environment name>",
  "project": {
    "id": <project id>,
    ...
  },
  "feature_states": [{...}]
}

[dabeeeenster]

@kyle-ssg I think we should add an Environment drop down here:

hook it up to the API, and then we're done.

[kyle-ssg]

#238 Frontend's done for this under the flag "clone_environment", just need backend.

[dabeeeenster]

This isnt working for me on staging.

1. Create new project
2. Create flag, default it to disabled.
3. Set flag as enabled in development env
4. Create new env, cloning dev env
5. New env has flag disabled. Expected it to be enabled.

[gagantrivedi]

The issue is the all the hooks installed on feature state are not aware of the cloning feature, and they fill the feature value with the default instead of using the cloned one.
One simple solution from top of my mind is too add something like source_env <fk to env> that can be used(if not null) by the hooks to copy the value. @matthewelwell what do you think?

[matthewelwell]

Yeah, that sounds like a smart idea to me.

[gagantrivedi]

Yeah, that sounds like a smart idea to me.

This may work for Feature state, but we have to copy segments and identities as well. and some of them don't have hooks.

[matthewelwell]

Ok, so we just need to do that in the clone method on the environment I guess?

[gagantrivedi]

Ok, so we just need to do that in the clone method on the environment I guess?

I am planning to implement clone method on Feature state, feature segments and feature identity. each clone method will be responsible for creating clone of itself with a different env

[dabeeeenster]

Data to copy:

• Feature States
• Segment Overrides

Make initiating user the Admin of that environment

Nothing else

[kyle-ssg]

As far as I can see, this still doesn't work - feature states are not copied over, at least currently in production. Also if it's behind a feature flag we should perhaps delay closing this until it's enabled.

[dabeeeenster]

Some data are not cloning correctly. E.g. I cloned this environment:

and this is what copied:

Note the background_colour config value is different.

[gagantrivedi]

@dabeeeenster can't reproduce. Can you list the steps?

[kyle-ssg]

Can no longer replicate, has this feature been deployed / adjusted in production since the 15th @gagantrivedi ?

[dabeeeenster]

Yep sorry I cant replicate this any more - closing