1. have `yarn` installed 2. have `nvm` installed (or node version 14) 3. use node version 14: `nvm use` 4. install packages: `yarn`.
Types and validators that help describe the model of a Backstage Catalog
A small, framework-agnostic JavaScript/TypeScript client for the Apache Iceberg REST Catalog
An isomorphic client for the catalog backend
Common functionalities for the catalog plugin
The plugin-catalog-node module for @backstage/plugin-catalog-backend
A frontend library that helps other Backstage plugins interact with the catalog
SQL ConnectionString parser
A module that subscribes to catalog related events and logs them.
The Backstage backend plugin that provides the Backstage catalog
The Backstage plugin for browsing the Backstage catalog
Adds support for the scaffolder specific entity model (e.g. the Template kind) to the catalog backend plugin.
Typed client for models.dev to fetch model catalogs with friendly errors.
A Backstage plugin the helps you import entities into your catalog
Parse catalog protocol specifiers and return the catalog name.
A public-facing copy of [error-catalog-nodejs](../error-catalog-nodejs) which copies most of the existing functionality while only disclosing non-internal errors to the published NPM package.
A Backstage catalog backend module that helps integrate towards GitHub
A module for the search backend that exports catalog modules
Tree-shakeable static models.dev catalog split by provider for TokenLens.
No description provided.
The github-org backend module for the catalog plugin.
https://www.npmjs.com/package/@segment/analytics-node
YAML language server
OCI NodeJS client for Service Catalog Service
Collect and export test cases as a catalog.
Proc macros for test catalog collection, see test-catalog for details
Test all your puppet catalogs for compiler warnings and errors.
Test all your puppet catalogs for compiler warnings and errors.
cucumber-puppet is a tool for behavioral testing of Puppet catalogs
A simple framework for creating a Test Data Catalog
As an aid when writing Puppet RSpec tests, you can dump the Puppet catalog in RSpec format
An RSpec formatter that allows you to write security focused tests for OSCAL catalogs and produce Assessment Plans and Assessment Results.
Octocatalog-Diff assists with Puppet development and testing by enabling the user to compile 2 Puppet catalogs and compare them. It is possible to compare different branches, different versions, and different fact values. This is intended to be run from a local development environment or in CI.
The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers.
`fingerpuppet` is a simple library and commandline tool to interact with Puppet's REST API without needing to have Puppet itself installed. This may be integrated, for example, into a provisioning tool to allow your provisioning process to remotely sign certificates of newly built systems. Alternatively, you could use it to request known facts about a node from your Puppet Master, or even to request a catalog for a node to, for example, perform acceptance testing against a new version of Puppet before upgrading your production master. Install the binford2k/fingerpuppet puppet module to get a class that can automatically configure your `auth.conf` file under Puppet Enterprise, where that file is managed.
The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers. Note that google-cloud-apigee_registry-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-apigee_registry instead. See the readme for more details.
## A mirror API for Ruby In various [research][p1] [projects][p2] the advantages of having a [mirror API][p3] to separate reflection from a language implementation have been discussed, and "industry grade" implementations exist for [Java][p4] and [C#][p5]. This project aims at providing a number of specs and classes that document a mirror API for Ruby. The mirror implementation that is part of this project will use only those language facilities that are available across Ruby implementations. The specs, however, will also test behavior that cannot be provided in such a manner. The idea here is that in time, all implementations provide their own implementation of the mirror API, and all implementations collaborate on this one spec. Why do this, you ask? Because Ruby needs tools, and those tools need to be written in Ruby. If they are not, then people will be excluded from tinkering with their tools, thus impeding innovation. You only have to look at Emacs or Smalltalk to see what's possible when programmers can extend their tools, all tools, in a language they feel comfortable in. If we have a standard mirror API, all tools that are written **for** Ruby, **in** Ruby, can be shared across implementations, while at the same time allowing language implementers to use the facilities of their platform to provide optimal reflective capabilities without tying them to internals. [p1]: http://www.cs.virginia.edu/~lorenz/papers/icse03/icse2003.pdf "Pluggable Reflection: Decoupling Meta-Interface and Implementation" [p2]: http://bracha.org/newspeak-spec.pdf "Newspeak Programming Language Draft Specification, Version 0.06, pages 40 onward" [p3]: http://www.hpi.uni-potsdam.de/hirschfeld/events/past/media/100105_Bracha_2010_LinguisticReflectionViaMirrors_HPI.mp4 "Linguistic Reflection Via Mirrors" [p4]: http://bracha.org/mirrors.pdf "Mirrors: Design Principles for Meta-level Facilities of Object-Oriented Programming Languages" [p5]: http://oreilly.com/catalog/progcsharp/chapter/ch18.html "See esp. 18-3, highlighting how C# reflection works on assembly rather than VM objects"
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.