Failure to deploy correctly. #18
Description
Using a trial instance of Automation Pilot stood up in early June 2024, the resulting YAML from a "Build Run Configuration" does not resulting in a running POD.
First issue is the environment variables passed in the spec are not named correctly. In release v0.0.4 the update to internal/kubernetes/metadata/metadata.go changed OPERATOR_ID, ENVIRONMENT, and INSTANCE_ID to RWP_OPERATOR_ID, RWP_ENVIRONMENT, and RWP_INSTANCE_ID but the generated YAML uses the older names without the RWP_
Second issue is the order of stanzas in the YAML seem to be off. In the spec section, adding the volume pointing to the secretName failed when the definition of the secret was in its default position at the bottom of the file. Even though the secret was created, the POD complained that it didn't exist. Moving the definition up to the second stanza (after Namespace) seemed to correct this. Other stanzas like the Service account didn't have an issue. Maybe a timing issue since the Secret is kind of large and my Kyma env is also a trial and therefore limited.
Last comment, there is mention of examples in the README.md, and I don't see any. As someone new to Automation Pilot and Kubernetes, would be nice to see examples of what can be done.