-
Suggestion
-
Resolution: Unresolved
Currently, the forge deploy command doesn't append an environment suffix to the validator created using the bitbucket-merge-check and bitbucket-dynamic-pipelines-provider templates. This causes confusion, as we cannot differentiate between development, staging, and production environments. The request is to enhance the implementation so that the environment suffix gets added to the validator.
[BCLOUD-23371] Add environment suffix to the forge validator created using the bitbucket-merge-check and bitbucket-dynamic-pipelines-provider templates
Labels | Original: ecohelp | New: ecosystem |
Description | Original: Currently, the forge deploy command doesn't append an environment suffix to the validator created using the bitbucket-merge-check and bitbucket-dynamic-pipelines-provider templates. This causes confusion, as we cannot differentiate between development, staging, and production environments. The request is to enhance the implementation so that the environment suffix gets added to the validator. | New: Currently, the {{forge deploy}} command doesn't append an environment suffix to the validator created using the {{bitbucket-merge-check}} and {{bitbucket-dynamic-pipelines-provider}} templates. This causes confusion, as we cannot differentiate between development, staging, and production environments. The request is to enhance the implementation so that the environment suffix gets added to the validator. |
Labels | New: ecohelp |
+1