fleet | fleet ties together systemd and etcd | Job Scheduling library

First, the code to append needs to go inside %sqlloop, if possible. If not, make a wrapper macro around %sqlloop, something like

Assuming your work.Vars contain data like this:

Consider extending your macro to receive such input parameters:

To the macro processor everything is text. So in your manual call you have included quotes in the values of the macro parameters. And in the CALL EXECUTE() statement you did not.

You can either re-write the macro to not require the quotes in the values. For example replace references like &fleet. with "&fleet.".

Or add the quote when generating the macro call.

In general in SAS you would define a macro to be able to rerun a multiple step process with different variables (or any other part of the code that needs to change). This is true whether the code you want to generate include PROC SQL steps or DATA steps or any other procedures.

Replace parts of the code that vary with references to macro variables. Wrap the code in a macro definition using those macro variables as the parameters. Then call the macro for each set of parameter values.

For example if you just wanted the input to be a single variable name your macro definition might look like:

For the spot fleet I think you need to setup that option in your launch template: AWS::EC2::LaunchTemplate CreditSpecification.

You are close. If you know that conditions do not overlap, you can just count them

You need to use dispatch(getUsersData()) instead of getUsersData() and it should work.

C++ is Unique_ptr pertinent for vectors of vectors

That's for you to decide, but only rapidly looking at the code without other knowledge of the infrastructure, I would say that this is a heavy, terrible code smell. I would simply use the vector as is. It's lighter, safer, simpler, and faster.

A pointer to a STL containe is usually a strong indicator of code smell, and a pointer to a STL container that contains pointer to STL containers has even a stronger code smell. This would simply not pass review and I would urge to simplify.

Owning pointers to STL containers should practically not exist in a code, unless there is some class that encapsulate very special memory management through container pointers, but they should not escape that class. And even then, you can manage memory and reuse with simple container values.

You should give value semantics a try! It helps local thinking and usually make code simpler.

Now for the non opinion based part of the question.

Let's drop the superfluous unique pointers in your code so it's easier to explain:

do this and fill in the alt for alternative text