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

Federated repository resources can not manage about "proxies" #838

Closed
kkitai opened this issue Oct 30, 2023 · 1 comment · Fixed by #848
Closed

Federated repository resources can not manage about "proxies" #838

kkitai opened this issue Oct 30, 2023 · 1 comment · Fixed by #848
Assignees
Labels
enhancement New feature or request

Comments

@kkitai
Copy link

kkitai commented Oct 30, 2023

Is your feature request related to a problem? Please describe.

I' m trying to do IaC artifactory federated repository with "artifactory_federated_generic_repository" resource having proxies configuration even though terraform.io document does not say that proxies(or proxy) scheme exists.
As I expected, terraform prints error when i run "apply".

❯ terraform apply
│ Error: Unsupported argument
│
│   on main.tf line 46, in resource "artifactory_federated_generic_repository" "federated-generic-test":
│   46:   proxy     = "test-proxy"
│
│ An argument named "proxy" is not expected here.
╵

Describe the solution you'd like

`artifactory_federated_*_repository" resources should have proxies(or proxy) scheme as well as WebUI can set.

Additional context
I'm using:

  • artifactory-provider v7.11.2
@alexhung alexhung self-assigned this Oct 30, 2023
@alexhung alexhung added the enhancement New feature or request label Oct 30, 2023
alexhung added a commit that referenced this issue Nov 17, 2023
…ed-repo

Add `proxy` and `disable_proxy` attributes to all federated repos
@kkitai
Copy link
Author

kkitai commented Nov 28, 2023

@alexhung thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants