Only use first API key output from get-api-key

[dav3r]

🗣 Description

This PR fixes a bug that can cause the PCA Gophish composition to fail to start up correctly.

💭 Motivation and context

If Gophish is configured to have multiple users, the get-api-key command (to the Gophish Docker service) will output multiple API keys, which was causing the gophish-init command to fail.

🧪 Testing

I tested this fix by making the same change to pca-gophish-composition.service in an assessment environment, then I added a second Gophish user and restarted the pca-gophish-composition.service. Without this fix, the service fails on startup, but with it, the service starts up cleanly.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All new and existing tests pass.

✅ Pre-merge checklist

• Finalize version.

✅ Post-merge checklist

• Add a tag or create a release.

[mcdonnnj]

This isn't a show-stopper, but I thought I would ask:

Should the SQL query in get-api-key be modified to only return one value instead? Should it be updated to get-api-keys to better represent that multiple keys might be returned? Should it be enhanced to return the API key associated with a given user?

[dav3r]

This isn't a show-stopper, but I thought I would ask:

Should the SQL query in get-api-key be modified to only return one value instead? Should it be updated to get-api-keys to better represent that multiple keys might be returned? Should it be enhanced to return the API key associated with a given user?

I thought about that too and wasn't sure what the best answer was. I think changing the name to get-api-keys is the simplest solution, but perhaps adding a username input makes more sense. I'm open to suggestions here.

[dav3r]

This isn't a show-stopper, but I thought I would ask:
Should the SQL query in get-api-key be modified to only return one value instead? Should it be updated to get-api-keys to better represent that multiple keys might be returned? Should it be enhanced to return the API key associated with a given user?

I thought about that too and wasn't sure what the best answer was. I think changing the name to get-api-keys is the simplest solution, but perhaps adding a username input makes more sense. I'm open to suggestions here.

After our team discussion earlier, I have created cisagov/gophish-docker#35 to address this issue. Thanks @mcdonnnj for mentioning this here!