[Feature Request] DABs: lifecycle bind

[aborsato-metco]

Description

The lifecycle tag is limited to prevent_destroy.
There are several other parameters that could make the lifecycle more useful to multi-environment configurations:

• behavior when the resource is deployed
• behavior when the resource is destroyed

This is an example of the lifecycle tag:

lifecycle:
  on_deploy:
    bind_if_exists: true
    mode: manage | reference # like terraform datasource
  on_destroy:
    preserve: true

Use Cases

• This approach would give us better control over what happens in mode: development or target specific. And we could use the resources bound (but not managed) as variable resolution in the DAB configuration.
• Developers could deploy a DAB in development mode, create a temp schema, test their pipelines, destroy the DAB after the branch is integrated into main where the official schemas (not managed by DAB) are.

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.