Skip to content

Add information about availability of packages in serverless projects#1516

Merged
jsoriano merged 9 commits intoelastic:mainfrom
jsoriano:status-serverless
Oct 19, 2023
Merged

Add information about availability of packages in serverless projects#1516
jsoriano merged 9 commits intoelastic:mainfrom
jsoriano:status-serverless

Conversation

@jsoriano
Copy link
Copy Markdown
Member

Extend elastic-package status to optionally include the packages available on each serverless project type.

For example, from the apache source directory:

$ elastic-package status --info serverless.project_types
Package: apache
Owner: elastic/obs-infraobs-integrations
Package Versions:
+-------------+---------+---------+--------------------+--------------------------------+--------------------------+
| ENVIRONMENT | VERSION | RELEASE |       TITLE        |          DESCRIPTION           | SERVERLESS PROJECT TYPES |
+-------------+---------+---------+--------------------+--------------------------------+--------------------------+
| Local       | 1.15.1  | GA      | Apache HTTP Server | Collect logs and metrics from  | -                        |
|             |         |         |                    | Apache servers with Elastic    |                          |
|             |         |         |                    | Agent.                         |                          |
+-------------+---------+---------+--------------------+--------------------------------+--------------------------+
| Production  | 1.15.1  | GA      | Apache HTTP Server | Collect logs and metrics from  | -                        |
|             |         |         |                    | Apache servers with Elastic    |                          |
|             |         |         |                    | Agent.                         |                          |
+-------------+---------+---------+--------------------+--------------------------------+--------------------------+
| Production  | 1.15.1  | GA      | Apache HTTP Server | Collect logs and metrics from  | observability            |
|             |         |         |                    | Apache servers with Elastic    |                          |
|             |         |         |                    | Agent.                         |                          |
+-------------+---------+---------+--------------------+--------------------------------+--------------------------+
| Production  | 1.15.1  | GA      | Apache HTTP Server | Collect logs and metrics from  | security                 |
|             |         |         |                    | Apache servers with Elastic    |                          |
|             |         |         |                    | Agent.                         |                          |
+-------------+---------+---------+--------------------+--------------------------------+--------------------------+

Fix #1343

@jsoriano jsoriano requested a review from a team October 19, 2023 10:27
@jsoriano jsoriano self-assigned this Oct 19, 2023
@elasticmachine
Copy link
Copy Markdown
Collaborator

💚 Build Succeeded

History

cc @jsoriano

Copy link
Copy Markdown
Contributor

@mrodm mrodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

I was wondering also if it would be interesting to add to this command a --format parameter to change how the output is rendered. So, it can be used in automatic processes (e.g. CI pipelines or other scripts), setting for instance --format json to check (would it be easier?) if a package is available in a specific serverless project.

With the actual command, it could also be achieved. Something like this could be working (just tested with the output in the description):

elastic-package status --info serverless.project_types | cut -d '|' -f 7 | tr -d ' ' | grep observability
observability

@jsoriano
Copy link
Copy Markdown
Member Author

I was wondering also if it would be interesting to add to this command a --format parameter to change how the output is rendered. So, it can be used in automatic processes (e.g. CI pipelines or other scripts), setting for instance --format json to check (would it be easier?) if a package is available in a specific serverless project.

With the actual command, it could also be achieved. Something like this could be working (just tested with the output in the description):

elastic-package status --info serverless.project_types | cut -d '|' -f 7 | tr -d ' ' | grep observability
observability

Good idea! Issue created for this #1519

@jsoriano jsoriano merged commit af6a093 into elastic:main Oct 19, 2023
@jsoriano jsoriano deleted the status-serverless branch October 19, 2023 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add tooling to discover on what Elastic offerings a package will be available

3 participants