Skip to content

Conversation

@mateumann
Copy link
Contributor

No description provided.

mateumann added 5 commits May 11, 2021 08:42
Force the new deployments created with "deploy-on" mechanism (a.k.a.
"into environments") have ids populated using UUID4 instead of a
template <environment>-<blueprint_id>-<uuid>.  The former solution might
have had caused excesively long deployment ids, especially in case of
multiple levels of environments, sub-environments (and services).
@mateumann mateumann merged commit a117f34 into master May 11, 2021
@mateumann mateumann deleted the RD-2287-deploy-on-id-and-naming-1 branch May 11, 2021 09:12
mateumann added a commit that referenced this pull request May 11, 2021
* Use UUID4 for deployment.ids "deployed-on"

Force the new deployments created with "deploy-on" mechanism (a.k.a.
"into environments") have ids populated using UUID4 instead of a
template <environment>-<blueprint_id>-<uuid>.  The former solution might
have had caused excesively long deployment ids, especially in case of
multiple levels of environments, sub-environments (and services).

* Populate display_name for new deployments

* Populate `csys-obj-parent` the same `csys-environment` used to be populated
mateumann added a commit that referenced this pull request May 11, 2021
* Use UUID4 for deployment.ids "deployed-on"

Force the new deployments created with "deploy-on" mechanism (a.k.a.
"into environments") have ids populated using UUID4 instead of a
template <environment>-<blueprint_id>-<uuid>.  The former solution might
have had caused excesively long deployment ids, especially in case of
multiple levels of environments, sub-environments (and services).

* Populate display_name for new deployments

* Populate `csys-obj-parent` the same `csys-environment` used to be populated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants