Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

Public Ansible Project Meeting Agenda - February 2020 #519

Closed
samdoran opened this issue Jan 30, 2020 · 14 comments
Closed

Public Ansible Project Meeting Agenda - February 2020 #519

samdoran opened this issue Jan 30, 2020 · 14 comments

Comments

@samdoran
Copy link
Contributor

Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped. If your IRC nick is different from your Github username, leave that as well.

See https://github.com/ansible/community/blob/master/meetings/README.md for the schedule

Once an item has been discussed it should get checked off.

If you just want reviewers for your contribution try the #ansible-devel irc channel on freenode.

@samdoran
Copy link
Contributor Author

samdoran commented Jan 30, 2020

Bringing over topics from #516

@felixfontein:

@pdumais
Copy link

pdumais commented Jan 30, 2020

@felixfontein
Copy link
Contributor

felixfontein commented Jan 30, 2020

@felixfontein
Copy link
Contributor

felixfontein commented Feb 8, 2020

@felixfontein
Copy link
Contributor

felixfontein commented Feb 8, 2020

@tremble
Copy link

tremble commented Feb 10, 2020

@pilou-
Copy link
Contributor

pilou- commented Feb 12, 2020

Once behavior has been decided, documentation could be improved:

  • scope of role params isn't documented, role params are only mentioned in the precedence list

  • scope of variables defined in defaults directory is mentioned here but the scope of variables defined in vars directory isn't mentioned here (it is mentioned in import_role documentation).

  • The documentation doesn't state that the variables defined with vars keyword below role: behave like variables defined in roels/<rolename>vars directory.

  • Is there any reason to use role variables instead of role parameters in the examples with role: ?

  • import_role doesn't allow to use role parameters: hence every role: keyword can not be replaced by import_role. However the current documentation states:

    • that:

      You can re-use roles statically anywhere in the tasks section of a play using import_role. The behavior is the same as using the roles keyword.

    • import_role doc

      Much like the roles: keyword

  • Scoping documentation is sparse:

    Play: each play and contained structures, vars entries (vars; vars_files; vars_prompt), role defaults and vars.

    vars entries isn't well defined (is the vars keyword of a task a vars entries ?)

  • vars keyword documentation doesn't mention that scope of import_role: vars differs from the scope of any other variables defined using vars keywords and another task.

@felixfontein felixfontein pinned this issue Feb 19, 2020
@gundalow
Copy link
Contributor

Ansible Contributors Summit EUROPE

What

Ansible Contributor Summit is a one day event especially for community contributors to meet with each other, as well as Ansible development teams (Core, AWX/Tower, Galaxy) in person, to discuss important issues in the community and help shape the future of Ansible. For those unable to make it to Gothenburg, we welcome you to join virtually for part/all of the day. Online participation and streaming details to follow closer to the summit.

When

  • Contributors Summit: Sunday, 29th March
  • Ansible Hackathon: Monday 30th March
  • FOSS-North: 30 & 31st March

How

  • If you plan to attend in person, please register on Eventbrite
  • If you plan to attend the hackathon or any of FOSS-North please register
  • If you plan to attend virtually details will be added to the Etherpad the day before

Agenda

@giner
Copy link

giner commented Mar 3, 2020

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants