Feature #901

package type not automatically dependant on yumrepo type

Added by Digant Kasundra over 4 years ago. Updated 3 days ago.

Status:Accepted Start date:
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:RAL
Target version:3.X
Affected Puppet version:0.24.7 Branch:
Keywords:
Votes: 1

Description

When using a yumrepo type to define yum repositories and using a yum provider for packages, there should be an automatic dependency setup between the two such that the yumrepo is processed first.

Related issues

blocked by Puppet - Feature #7240: Split up collecting and realizing. Accepted 04/26/2011

History

#1
Updated by Luke Kanies over 4 years ago

  • Status changed from 1 to 2

#2
Updated by Luke Kanies over 4 years ago

This is actually more difficult than normal automatic relationships, because it involves a relationship to all members of a class, rather than specifically named members.

This will be much easier in the next release, since it completely redoes how resources are found and referred to, so I’m bumping this.

#3
Updated by Redmine Admin almost 4 years ago

  • Status changed from 2 to Accepted

#4
Updated by Luke Kanies about 3 years ago

  • Target version changed from 0.25.0 to 2.6.0
  • Affected Puppet version set to 0.24.7

At the least, this should be much easier to do with #1088 being fixed.

Given that this is still a big change and is unrelated to the major push in 0.25, I’m bumping.

#5
Updated by James Turnbull over 2 years ago

  • Target version changed from 2.6.0 to 2.7.x

#6
Updated by Luke Kanies about 2 years ago

  • Assignee deleted (Luke Kanies)

#7
Updated by Nigel Kersten about 1 year ago

  • Target version changed from 2.7.x to 3.X

This is still difficult until #7240 is addressed.

If you don’t use virtual resources, you can use the new collection syntax for expressing this

YumRepo <| |> -> Package <| |>

but be warned that this will realize any virtual resources in the process of setting up the relationship.

#8
Updated by Matthew Black 3 days ago

Digant Kasundra wrote:

When using a yumrepo type to define yum repositories and using a yum provider for packages, there should be an automatic dependency setup between the two such that the yumrepo is processed first.

If I might add to the issue. I’m in the process of migrating from Redhat to SuSE and this feature would be greatly appreciated for other type of repositories but currently only yumrepo is supported out of box. It would almost be good to have a generic resource type for repositories, similar to how package resource type is, and have a provider tag for the type of repository.

Also available in: Atom PDF