Namespace ID and secret key should be got whatever the separator between Namespace ID and secret key in secret ID.
Or theses informations should be got in another ways.
Actual Behaviour
Namespace ID and secret key are retrieved from secret ID, namespace ID is equals to the first part before the first underscore and the secret key is equals to the other part.
When the namespace ID contains underscores, parsing these informations is not done correctly.
Steps To Reproduce
Create a namespace secret in a namespace containing underscores in its name, and try to update the secret.
tchiotludo
commented
1 year ago
Expected Behavior
Namespace ID and secret key should be got whatever the separator between Namespace ID and secret key in secret ID. Or theses informations should be got in another ways.
Actual Behaviour
Namespace ID and secret key are retrieved from secret ID, namespace ID is equals to the first part before the first underscore and the secret key is equals to the other part. When the namespace ID contains underscores, parsing these informations is not done correctly.
Steps To Reproduce
Create a namespace secret in a namespace containing underscores in its name, and try to update the secret.
Environment Information
Example flow
resource "kestra_namespace_secret" "secret_test" { namespace = xxxx.yyyy.my_fake_namespace secret_key = "kestra" secret_value = "rocks" }