Templates for OpenStack Antelope version

[jouvin]

Templates for Antelope are the first to implement the new repository layout (#62). Fixes #1.

[jouvin]

Layout change postponed until all panlint / indent errors are fixed.

[jouvin]

@jrha I'm trying to fix all the formatting issues, cleanup really needed in these templates! I need to put a few exceptions for lines too long in bind or prefix statements for example but it seems the line is not taken into account. For example features/placement/uwsgi/config.pan:22. Did I make something wrong?

There is also the issue I already mentioned with text in multiline annotations being parsed like in types/openstack/glance.pan but if I remember it is a bug not yet fixed...

[jouvin]

@jrha when you are done with the 24.10.0 release, I'd like your suggestions on how to fix the remaining panlint errors. I have the feeling that they are due to panlint flaws... but it may also be a mistake of mine!

• Line too long for unsplittable lines: I added the following panlint directive which doesn't seem to be taken into accout. Did I miss something?

  # panlint disable=LP006
  

• 'Trailing /in a parameter value where it is required: how to directpanlint` to ignore it

• Request to add spaces around - in an annotation: looks like a bug...

[jouvin]

@jrha a reminder that your advice is needed!

[jrha]

The line length checks are supposed to to indicate that something isn't being written as clearly as it could be, so I've made some suggestions that I think improve readability.

There are still some lines while will be unavoidably long, particularly the code that drops patch files into the Python path, which in general seems a bit worrying.

[jouvin]

@jrha thanks for your suggestions, I've been able to fix most of the problems. 2 issues remain but I'm afraid there is no workaround:

• 'Trailing /in a parameter value where it is required: how to directpanlint` to ignore it
• A few lines too long in features/magnum/k8s-fragment-fixes.pan prefix lines due to the long file paths involved: is there a panlint directive to exclude them? Or is it possible that panlint ignores this error if the path is entirely enclosed between {} (which means it canot be broken in several pieces).

[jrha]

If this PR can wait until the various panlint PRs are merged then I think we'll be able to deal with these remaining warnings in a sensible way.

[jouvin]

Yes sure! It can allow to test the the issues are properly solved.

[jrha]

quattor/pan#278 adds support for suppressing checks on specific lines.

[jrha]

Rebased on main and updated panlint suppression comments.