* 🎉 New implementation for AWS Secret Manager for issue
#10518
Added new implementation AWSSecretManagerPersistence and integration tests AWSSecretManagerPersistenceIntegrationTest
A new implementation of SecretPersistence to support AWS Secret Manager AWSSecretManagerPersistence
New Integration tests as suggested on the open Issue, similar to GCP secret manager
* Updated version to `aws-secretsmanager-caching-java:1.0.2`
- Added new argument check for AWS Secret Manager.
* exclude jackson-databind from aws dependency and run gradle format
* bump aws-related dependencies to prevent old version of jackson-databind from being pulled in
* - Added new entry for `AWS_SECRET_MANAGER` into SecretPersistence.java
- Externalized configurations for AWS Secret Manager into Configs and EnvConfigs.java as requested.
- Adjusted test to use new constructor for `AWSSecretManagerPersistence`
- Augmented instructions configuring-airbyte.md with the new config keys.
* Formatting code.
* revert dependency version bump
Co-authored-by: pmossman <parker@airbyte.io>
Co-authored-by: mauricioalarcon <unknown>
* sweep all scheduler application code and new-scheduler conditional logic
* remove airbyte-scheduler from deployments and docs
* format
* remove 'v2' from github actions
* add back scheduler in delete deployment command
* remove scheduler parameters from helm chart values
* add back job cleaner + test and add comment
* remove now-unused env vars from code and docs
* format
* remove feature flags from web backend connection handler as it is no longer needed
* remove feature flags from config api as it is now longer needed
* remove feature flags input from config api test
* format + shorter url
* remove scheduler parameters from helm chart readme
* adding env config JOB_KUBE_SIDECAR_CONTAINER_IMAGE_PULL_POLICY to support image pull policy on sidecar containers
* add documentation
* docs: adding more description and trying to force cla check.
* docs: fix wording
This PR adds the possibility to define pod annotations to the pods created by the workers.
Pod annotations can be required in different situations, such as configuring which IP pool to use when using some network plugins.
The original PR was here: #9874 we decided to split it into 3 different PRs.
