The tap-nasa
                  extractor
                    pulls data from
                    NASA that can
                    then be sent to a destination using a
                    loader. 
                      Airbyte Usage Notice
                    
                    Container-based connectors
                    can introduce deployment challenges including the potential need to run
                    Docker-in-Docker (not currently supported by services like AWS ECS, Meltano
                    Cloud, etc. see
                    FAQ
                    and
                    Airbyte's ECS deployment docs
                    for more details). Before using this variant we recommend considering if/how
                    you will be able to deploy container-based connectors to production.
                    
                    For more context on how this Airbyte integration works please checkout out the
                    FAQ in the Meltano Docs.
                    
Getting Started
Prerequisites
If you haven't already, follow the initial steps of the Getting Started guide:
Installation and configuration
- 
                      Add the tap-nasa extractor to your
                      project using
                      
:meltano add - 
                        Configure the tap-nasa
                        settings using
                        
:meltano config - 
                        Test that extractor settings are valid using
                        
:meltano config 
meltano add extractor tap-nasameltano config tap-nasa set --interactivemeltano config tap-nasa testNext steps
Follow the remaining steps of the Getting Started guide:
If you run into any issues, learn how to get help.
Capabilities
      The current capabilities for
      tap-nasa
      may have been automatically set when originally added to the Hub. Please review the
      capabilities when using this extractor. If you find they are out of date, please
      consider updating them by making a pull request to the YAML file that defines the
      capabilities for this extractor.
    
This plugin has the following capabilities:
- about
 - catalog
 - discover
 - schema-flattening
 - state
 - stream-maps
 
      You can
      override these capabilities or specify additional ones
      in your meltano.yml by adding the capabilities key.
    
Settings
      The
      tap-nasa settings that are known to Meltano are documented below. To quickly
      find the setting you're looking for, click on any setting name from the list:
    
airbyte_config.api_keyairbyte_config.concept_tagsairbyte_config.countairbyte_config.end_dateairbyte_config.start_dateairbyte_config.thumbsairbyte_spec.imageairbyte_spec.tagdocker_mounts
Expand To Show SDK Settings
      You can also list these settings using
      
      with the meltano configlist
      subcommand:
    
meltano config tap-nasa list
      You can
      override these settings or specify additional ones
      in your meltano.yml by adding the settings key.
    
Please consider adding any settings you have defined locally to this definition on MeltanoHub by making a pull request to the YAML file that defines the settings for this plugin.
Airbyte Config Api Key (airbyte_config.api_key)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_CONFIG_API_KEY 
API access key used to retrieve data from the NASA APOD API.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_config api_key [value]- 
          Environment variable:
          
TAP_NASA_AIRBYTE_CONFIG_CONCEPT_TAGS 
Indicates whether concept tags should be returned with the rest of the response. The concept tags are not necessarily included in the explanation, but rather derived from common search tags that are associated with the description text. (Better than just pure text search.) Defaults to False.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_config concept_tags [value]Airbyte Config Count (airbyte_config.count)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_CONFIG_COUNT 
A positive integer, no greater than 100. If this is specified then count randomly  chosen images will be returned in a JSON array. Cannot be used in conjunction with  date or start_date and end_date.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_config count [value]Airbyte Config End Date (airbyte_config.end_date)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_CONFIG_END_DATE 
Indicates that end of a date range. If start_date is specified without an end_date then end_date defaults to the current date.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_config end_date [value]Airbyte Config Start Date (airbyte_config.start_date)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_CONFIG_START_DATE 
Indicates the start of a date range. All images in the range from start_date to  end_date will be returned in a JSON array. Must be after 1995-06-16, the first day an APOD picture was posted. There are no images for tomorrow available through this API.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_config start_date [value]Airbyte Config Thumbs (airbyte_config.thumbs)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_CONFIG_THUMBS 
Indicates whether the API should return a thumbnail image URL for video files. If set to True, the API returns URL of video thumbnail. If an APOD is not a video, this parameter is ignored.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_config thumbs [value]Airbyte Spec Image (airbyte_spec.image)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_SPEC_IMAGE - 
          Default Value: 
airbyte/source-nasa 
Airbyte image to run
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_spec image [value]Airbyte Spec Tag (airbyte_spec.tag)
- 
          Environment variable:
          
TAP_NASA_AIRBYTE_SPEC_TAG - 
          Default Value: 
latest 
Airbyte image tag
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set airbyte_spec tag [value]Docker Mounts (docker_mounts)
- 
          Environment variable:
          
TAP_NASA_DOCKER_MOUNTS 
Docker mounts to make available to the Airbyte container. Expects a list of maps containing source, target, and type as is documented in the docker --mount documentation
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set docker_mounts [value]Expand To Show SDK Settings
Flattening Enabled (flattening_enabled)
- 
              Environment variable:
              
TAP_NASA_FLATTENING_ENABLED 
'True' to enable schema flattening and automatically expand nested properties.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set flattening_enabled [value]Flattening Max Depth (flattening_max_depth)
- 
              Environment variable:
              
TAP_NASA_FLATTENING_MAX_DEPTH 
The max depth to flatten schemas.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set flattening_max_depth [value]Stream Map Config (stream_map_config)
- 
              Environment variable:
              
TAP_NASA_STREAM_MAP_CONFIG 
User-defined config values to be used within map expressions.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set stream_map_config [value]Stream Maps (stream_maps)
- 
              Environment variable:
              
TAP_NASA_STREAM_MAPS 
Config object for stream maps capability. For more information check out Stream Maps.
Configure this setting directly using the following Meltano command:
meltano config tap-nasa set stream_maps [value]Something missing?
This page is generated from a YAML file that you can contribute changes to.
Edit it on GitHub!Looking for help?
#plugins-general
    channel.
  

