puppetlabs / puppetlabs/puppetlabs-docker
[3.9.1] Deferred/Sensitive not woking for docker::registry
Open
community
stale
- Dominant language
- Ruby
- Stars
- 94
- Forks
- 337
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 2
Description
When using the Deferred function of puppet it will fails on docker::registry.
Sample code:
docker::registry { 'foo':
username => Deferred(foo_function, [foo_option]),
password => Deferred(foo_function, [foo_option]),
}
will fails with:
parameter 'username' expects a value of type Undef or String, got Deferred
parameter 'password' expects a value of type Undef or String, got Deferred
The same will happens when using Sensitive(Deferred(..))
parameter 'username' expects a value of type Undef or String, got Sensitive[Deferred]
parameter 'password' expects a value of type Undef or String, got Sensitive[Deferred]
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 at the docker::registry resource and reproduce the reported Deferred and Sensitive(Deferred) examples. Review linked pull request #1066 for the work already underway; the issue is done when both username and password accept these values without the shown type errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100