Able to create KVMs for non-existent environments - intended behaviour?

[Huw]

We've been trying out the KVM API for Apigee X but have noticed a very strange feature.

You can create key value maps and entries in non-existent environment.  While this isn't an issue, I wonder is it an intentional design decision?

It did make debugging an automated deployment difficult because the KVM create succeeded even though we'd got the environment name wrong.

Here's what I mean, you can do:

GET https://apigee.googleapis.com/v1/organizations/<your-org>/environments/

returns 2 environments:

[
"env-one",
"env-two"
]

but you can query key value maps for any other environment name.

GET https://apigee.googleapis.com/v1/organizations/<your-org>/environments/<any-env-name>/keyvaluemaps/

returns an empty KVM set:

[]

but you can then POST, GET, DELETE new KVMs and entries and it will populate them

[dknezic]

Thanks for raising this. I was also able to reproduce the behaviour you're seeing, and have raised this as an issue internally (268150348).