getOperate
CLI and push to a getOperate workspace this works using the CLI doing getOperate sync push --raw
(non-EE)
getOperate sync pull --raw
(EE). Having it commit back to getOperate has 2 benefits:
--skip-variables --skip-secrets --skip-resources
to avoid syncing them. This is because variables, resources and secrets should
have values that are specific to each environment. For instance, a resource
named f/myproject/myimportantdb
should have a different value in staging and
prod. This is why they are not synced and should be set manually in each
environment. You can however if you prefer, manually sync those. Do note that
secrets have an additional layer of encryption and are by default exported in
their encrypted form whose decryption key is workspace specific. To sync them
between workspace, use --plain-secrets
to export them in plain text.goprt_deploy/[WORKSPACE_NAME]/[SCRIPT_PATH]
(for instance goprt_deploy/staging/f/example/script
)