René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Placeholder for version 5 of config.yml","articleBody":"Work has started with the syntax for version ~3~ ~4~ 5 of config.yml.\n\nThis issue will be used a placeholder to link with other issues and feature request as well a providing a place for discussion (in addition to slack).\n\nThe current draft version of Configuration Syntax v5 can be found [here](https://github.com/gitlabform/gitlabform/wiki/Configuration-Syntax-v5-Draft) in our wiki.\n\n**Requirements:**\n\n-  [ ] YAML 1.2\n  - [ ] highlight use of node anchors\n- [ ] jinja2 templates (possibly with the use of dynaconf)\n  - [ ] [built-in filters](https://jinja.palletsprojects.com/en/3.0.x/templates/#builtin-filters)\n  - [ ] standard custom filter ENV for environment variables\n  - [ ] any other custom filter?\n  - [ ] what’s needed to handle different input data formats for rendering (json, yaml, xml etc)?\n- [ ] work with document separator “---”\n- [ ] work with multiple files, e.g. gitlabform file1 file2 file3\n- [ ] prepare to minor adaptation of format when GitLab merges groups and projects into [namespaces](https://forum.gitlab.com/t/restructure-gitlab-with-namespaces-work-items-etc/64229/3)\n  - [ ] can we be backwards-compatible with or will the API change so that there will have to be two versions of gitlabform (pre- [ ] and post-namespaces)?\n- [ ] work with personal projects\n- [ ] inheritance:\n  - [ ] do-not-allow-inherit-overwrite\n  - [ ] do-not-inherit\n\n**Questions:**\n\n- [~] Shall we plan for use of python-gitlab?\n- [ ] Shall we plan for update, add and delete?\n  - [ ] Currently gitlabform support update with a exception (add/delete) for keys and variables \n  - [ ] with python-gitlab it should be easier to support add and delete\n- [ ] How should inheritance be combined with group/project members and “enforce”?\n- [ ] GitLab mixes update and edit? Shall we use their mix or just settle for one of them? (follow-up: @jimisola )\n- [ ] members: both project and groups?\n  - [ ] group_ldap_links: can only be applied to groups or projects as well? only groups\n  - [ ] What is this for: https://docs.gitlab.com/ee/api/groups.html#create-a-link-to-share-a-group-with-another-group ?\n    - [ ] Invite members\n    - [ ] Invite groups\n    - [ ] sync with LDAP groups\n- [ ] tags: belongs to project? **Yes.**\n- [ ] what terminology to use for variables vs secret_variables vs cicd_variables: variables (@gdubicki this is already in v3 right?)\n- [ ] keys/names of groups and projects\n- [ ] Services API → Integrations API: (@gdubicki this is already in v3 right?)\n\nRelevant links:\n* Idea for custom YAML resolver (pyyaml): [here](https://github.com/yaml/pyyaml/issues/457)  \n\n","author":{"url":"https://github.com/jimisola","@type":"Person","name":"jimisola"},"datePublished":"2022-02-05T20:23:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/331/gitlabform/issues/331"}