spring-cloud / spring-cloud/spring-cloud-config
Found what looks like an issue with spring.cloud.config.awsS3 with multiple profiles
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
I have a application.yml and 4 more files application-local.ym, application-dev.yml, application-qa.yml, application-prod.yml. The way it works is that
spring:
profiles:
active:
@activatedProperties@
Will depending on what @activatedProperties@ is, will pull the correct application so if @activatedProperties@ is local, it will pull application-local.ym.
The problem is that to run
cloud:
config:
server:
awss3:
bucket: hp-fetcher-config
region: us-west-2
order: 1
I need to replace
spring:
profiles:
active:
@activatedProperties@
with
spring:
profiles:
active:
awss3
I cant find any docs or examples that show how to run awss3 in multiple profiles
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the spring.cloud.config.server.awss3 configuration and the profile activation examples described in the issue. Determine whether multiple profiles are supported with AWS S3 and document the required configuration or the limitation, including a working example if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100