Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use existing content source for templates if one exists for project #448

Closed
Michaelpalacce opened this issue Oct 10, 2024 · 1 comment
Closed
Assignees
Labels
area/artifact-manager Relates to the `artifact-manager` maven module effort/medium kind/enhancement Enhancement or improvement of existing features lang/java Related to Java Code priority/medium triage/accepted The issue was accepted and will be done version/minor Introduces a non-breaking feature or change

Comments

@Michaelpalacce
Copy link
Collaborator

Michaelpalacce commented Oct 10, 2024

Description

Content Sources are a bit unique in Aria Automations Service Broker.

When creating a Content Source for a project that points to Cloud Templates in Assembler, then you are limited to exactly one content source. Attempting to create more leads to the attempt failing.

As such, the proposal is to use an already existing content source if one is present on the system.

There are 2 ways to achieve this:

  1. Reactively - where the default will be used when a specific error is caught from the API.
  2. Proactively - where we check if a content source already exists for Assembler Cloud Templates and use that instead.

NOTES:

  • Only do this for Assembler Cloud Templates, not for other content sources.
  • Log a warning
@Michaelpalacce Michaelpalacce added kind/enhancement Enhancement or improvement of existing features lang/java Related to Java Code area/artifact-manager Relates to the `artifact-manager` maven module version/minor Introduces a non-breaking feature or change triage/accepted The issue was accepted and will be done priority/medium effort/medium labels Oct 15, 2024
@Michaelpalacce Michaelpalacce self-assigned this Nov 12, 2024
@Michaelpalacce
Copy link
Collaborator Author

This doesn't seem to be an issue... this currently works as expected and the correct CS is used

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/artifact-manager Relates to the `artifact-manager` maven module effort/medium kind/enhancement Enhancement or improvement of existing features lang/java Related to Java Code priority/medium triage/accepted The issue was accepted and will be done version/minor Introduces a non-breaking feature or change
Projects
None yet
Development

No branches or pull requests

1 participant